[Vincent Tran]

FYI, fixed by purging the cache between stopping the process and starting it back up.

[Vincent Tran]

I’m not sure if this is related…

Last month I noticed our Cloverleaf vmware instance shut down sometimes during the night. The image was stored on a Raid 5 disk configuration.

Due to some hard drive errors, I actually had to reformat/reinstall everything onto the machine. This time I used logical volume mounts instead of Raid and the Cloverleaf vmware instance runs now without shutting down every night.

– Vincent

[Vincent Tran]

That too generates an empty xml segment.

However for non empty fields in the VRL, it does not output the XML segment using set xlateOutVals

[Vincent Tran]

That generates the empty XML segment as well.

[Vincent Tran]

Thanks for the reply Jim.

The XML schema/dtd is fine because I use it for HL7 to XML xlate.

This is interesting, I echo $xlateInVals and it prints out {}

If I go:

set xlateOutVals $xlateInVals

although the value of $xlateInVals is {}, it still generates the empty xml segment.

However if I go:

set xlateOutVals {}

it doesn’t generate the empty xml segment like it is suppose to.

[Vincent Tran]

I encountered the same problem yesterday. I could start/stop existing sites, but when I initialize a new site and try starting up threads, it would result in that same error.

Solution that worked for me:

If I rename/delete the monitorShmemFile to something else, then it works fine the next time I try to start/stop the threads.

[Vincent Tran]

Cloverleaf includes it’s own Java runtime. I believe it uses Java 5.0 for version 5.5.

[Vincent Tran]

http://www.hl7.org.za/patient/ch700071.htm

I found this on the net. If you go through the slides it kind of explains how to decode it. Once you learn how to decode the wave form, you can use Java or TCL code to create the images. Should be possible, just involves a lot of work.

[Vincent Tran]

Is the wave form report very cryptic? Or is it just x, y points.

[Vincent Tran]

I’ve never done it before but am interested in how you would do this in Cloverleaf.

If I am correct, it is not possible to code a protocol to be selected in the protocol drop down. So maybe you would code a pdl, using the pdl-tcpip protocol. I know the minimum lower layer protocol (mlp-tcpip.pdl) retrieves the message data between 0x0b, 0x1c0x0d bytes. Perhaps you can copy this code but change it to retreive the message data between some html tags.

[Vincent Tran]

I think it is used for a cluster of Cloverleaf machines. Anyone know for sure?

[Vincent Tran]

Okay, so one of my prototypes involves a query response using a web service.

It takes about 1.25 seconds to call the web service through a Java UPOC. This places the results in memory so it can be read using a Read Java UPOC. Since the minimal time for a Read upoc is 1 second, it averages around 0.5 seconds to read the results. The queuing of messages in Cloverleaf adds another 1 to 2 seconds.

I’m trying to shorting the response time as much as possible, since one of the target query response times is three seconds (which may be impossible ~_~).

Currently I have an inbound and outbound thread. Perhaps since web service results come right after a method call, I can just use one inbound thread. After the xlate, I can call a post tps and do the web service query. Is it possible to place a message on the message queue to be sent back to the inbound client, even though your TPS code is being called on the thread outbound?

[Vincent Tran]

Hm, from reading this http://wiki.tcl.tk/10168” class=”bbcode_url”>http://wiki.tcl.tk/10168

It says

Quote:

if last is greater than or equal to the length of the string then it is treated as if it were end.

So if you had a string less than three characters like “ab”, then it would return “ab”

[Vincent Tran]

Thanks for the advise, but I am just prototyping and brainstorming ideas regarding query response. So I don’t have any problems yet.

I was also thinking that if the xlate could be called through the API’s, I could use Cloverleaf to write Xlate’s for stand-alone translation applications.

[Vincent Tran]

So that the message won’t be queued for translation, then queued again to be sent. Removes a bit of the queuing delay for query type messages where the User is waiting for the response.

[Author]

Replies